Crate nickel_lang_core

Modules

• cache
  Source cache.
• deserialize
  Deserialization of an evaluated program to plain Rust types.
• destructuring
  In this module, you have the main structures used in the destructuring feature of nickel. Also, there are implementation managing the generation of a contract from a pattern.
• environment
  An environment for storing variables with scopes.
• error
  Error types and error reporting.
• eval
  Evaluation of a Nickel term.
• identifier
  Define the type of an identifier.
• label
  Define the type of labels.
• parser
• position
  Define types of positions and position spans.
• pretty
• program
  Program handling, from file reading to evaluation.
• repl
  The Nickel REPL.
• serialize
  Serialization of an evaluated program to various data format.
• stdlib
  Load the Nickel standard library in strings at compile-time.
• term
  AST of a Nickel expression.
• transform
  Various post transformations of nickel code.
• typecheck
  Typechecking and type inference.
• types
  Define the Nickel type system.

Macros

• match_sharedterm
  Allows to match on SharedTerm without taking ownership of the matched part until the match. In the else clause, we haven’t taken ownership yet, so we can still use the richterm at that point.
• mk_app
  Multi-ary application for types implementing Into<RichTerm>.
• mk_array
  Array for types implementing Into<RichTerm> (for elements). The array’s attributes are a trailing (optional) ArrayAttrs, separated by a ;. mk_array!(Term::Num(42)) corresponds to \[42\]. Here the attributes are ArrayAttrs::default(), though the evaluated array may have different attributes.
• mk_fun
  Multi argument function for types implementing Into<Ident> (for the identifiers), and Into<RichTerm> for the body.
• mk_match
  Switch for types implementing Into<Ident> (for patterns) and Into<RichTerm> for the body of each case. Cases are specified as tuple, and the default case (optional) is separated by a ;: mk_switch!(format, ("Json", json_case), ("Yaml", yaml_case) ; def) corresponds to match { 'Json => json_case, 'Yaml => yaml_case, _ => def} format.
• mk_opn
  Multi-ary application for types implementing Into<RichTerm>.
• mk_record
  Multi field record for types implementing Into<Ident> (for the identifiers), and Into<RichTerm> for the fields. Identifiers and corresponding content are specified as a tuple: mk_record!(("field1", t1), ("field2", t2)) corresponds to the record { field1 = t1; field2 = t2 }.
• mk_uty_arrow
  Multi-ary arrow constructor for types implementing Into<TypeWrapper>.
• mk_uty_enum
  Wrapper around mk_uty_enum_row! to build an enum type from an enum row.
• mk_uty_enum_row
  Multi-ary enum row constructor for types implementing Into<TypeWrapper>. mk_uty_enum_row!(id1, .., idn; tail) correspond to `<id1, .., idn | tail>.
• mk_uty_record
  Wrapper around mk_uty_record! to build a record type from a record row.
• mk_uty_row
  Multi-ary record row constructor for types implementing Into<TypeWrapper>. mk_uty_row!((id1, ty1), .., (idn, tyn); tail) correspond to `{id1: ty1, .., idn: tyn | tail}. The tail can be omitted, in which case the empty row is uses as a tail instead.